Skip to content

Conversation

@HolgerKnublauch
Copy link
Contributor

Closes #587

The PR is large because it includes some fixes to the layout of various examples (tabs vs spaces, aligned use of blocks).

@afs afs changed the title Issue 587 GH-587: shnex:where node expression Oct 14, 2025
@HolgerKnublauch HolgerKnublauch changed the title GH-587: shnex:where node expression GH-587: shnex:nodesWhere node expression Oct 20, 2025
@HolgerKnublauch HolgerKnublauch added the Node Expressions For SHACL 1.2 Node Expressions label Oct 20, 2025
@HolgerKnublauch
Copy link
Contributor Author

May I get some feedback on this PR please?

@afs
Copy link
Contributor

afs commented Nov 4, 2025

May I get some feedback on this PR please?

See comments on the issue about naming.

"nodesWhere" does not lead to a natural syntax in the rule language. "match", as originally proposed, does.

.


# Nodes Where Expressions -----------------------------------------------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If every Nodes Where is case-sentively replaced with Nodes Matching, I think @afs will be satisfied, and general comprehension improved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@afs would shnex:nodesMatching work for you?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

Copy link
Contributor

@recalcitrantsupplant recalcitrantsupplant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me.

</aside>
<p>
The interpretation of <code>shnex:nodesMatching</code> is similar to <code>sh:targetWhere</code>.
The main differences are that <code>sh:targetMatching</code> is part of SHACL Core and that
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be sh:targetWhere instead of sh:targetMatching.

Changed sh:targetMatching to sh:targetWhere.
Copy link
Contributor

@robert-david robert-david left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed sh:targetMatching to sh:targetWhere.

@HolgerKnublauch HolgerKnublauch merged commit d316c89 into gh-pages Nov 11, 2025
1 check passed
@HolgerKnublauch HolgerKnublauch deleted the issue-587 branch November 11, 2025 11:16
afs pushed a commit that referenced this pull request Nov 17, 2025
* #587: Added shnex:where

* Formatting (including unrelated examples)

* Renamed from shnex:where to shnex:nodesWhere

* Applied PR feedback

* Renamed nodesWhere to nodesMatching

* Update index.html

Changed sh:targetMatching to sh:targetWhere.

---------

Co-authored-by: Robert David <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Node Expressions For SHACL 1.2 Node Expressions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"match shapes" node expression

6 participants